Reason for that is that `a || b` will expand to:

```
case a do
  val when val in [false, nil] -> b
  val -> val
end
```

Which is harder to optimise by the compiler. `or/2` works only with
booleans, so in places where we do not care about returned value or
`nil` cases, it is better to use `or/2`.

* ft: improve socket metrics gathering

As we are only interested in just 2 of the values from the socket stats, fetch
only these. This should reduce time required for processing data sent between
port and application. It also simplifies pattern matching and data extraction.

* ft: gather metrics from other nodes with low priority

* chore: update Benchee

* chore: unlock telemetry_metrics

* chore: remove unused libraries from lockfile

* chore: update Rustler and Rust dependencies

* chore: update direct dependencies

* chore: upddate Phoenix.LiveView

Supavisor is not using any HTML views, it do not offer any HTML-based
UI, etc. so these functionalities aren't needed for anything.

I have used [`typos`][typos] tool to find all typos in source code over
the codebase.

[typos]: https://github.com/crate-ci/typos

* chore: add Nix Flake to project

Currently it defines only development environment for Supavisor. In the
future the plan is to add package definition as well as NixOS module to
the Flake. This will simplify deployment on NixOS platforms as well as
should help with spawning virtual machines with Supavisor running on
them.

* ft: add derivation for Supavisor

All changes required by our code are merged to mainline, so we do not
need to use custom fork anymore.

feat: shorter retry connect timeout for proxy mode

This will raise if there are some pending changes to the `mix.lock`.
This is to ensure, that `mix.lock` was uploaded after dependency
changes.

* fix: update max clients error in session mode

That tests are constantly causing us problems in CI, but as it is test
for internal functionality that do not affect users directly. So to
streamline testing disable running these tests in default run. To run
them one can use

    mix test --include flaky

…478)

These plugs weren't used at all, as we do not serve any static assets nor we
need live reload for anything (as we do not have any form of web UI).

Handle errors during authentication query gracefully and shutdown
the client process to not leave the hanging connections.

* test: increase pool size in external test suite to match nano instances

* test: make timeouts configurable

* test: disable prepared transactions test, as these are disabled for security reasons

* test: disable cursor tests in transaction mode

* test: disable custom socket test

* test: disable MAX_PARAMETERS_EXCEEDED test

* test: disable query format errors test

* test: run connection reserving test only in session mode

* test: make Postgres.js more verbose

* test: ensure connections with different parameters are available where needed

* test: fix typo in test name

This allows us to use this piece of code in function head in pattern
match. This reduces places where the magic value is required and make
the code a little bit neater and cleaner.